home *** CD-ROM | disk | FTP | other *** search
- Path: news1.h1.usa.pipeline.com!usenet
- From: grantp@usa.pipeline.com(Pete)
- Newsgroups: comp.lang.c
- Subject: Re: Why does a compiled program fail on another machine?
- Date: 3 Jan 1996 06:39:37 GMT
- Organization: Kalevi, Inc
- Message-ID: <4cd8b9$aor@news1.usa.pipeline.com>
- NNTP-Posting-Host: pipe4.h1.usa.pipeline.com
- X-PipeUser: grantp
- X-PipeHub: usa.pipeline.com
- X-PipeGCOS: (Pete)
- X-Newsreader: Pipeline USA v3.3.0
-
- On Jan 03, 1996 02:06:46 in article <Why does a compiled program fail on
- another machine?>, 'Douglas John Standen <John@metsys.demon.co.uk>' wrote:
-
-
- >Having written and run a quite complex program, I find that it
- >works perfectly on my 386/22 every time, but fails on my friends
- >486 with acos domain error.
-
- Don't know what an "acos domain" error is -- but I do know it has
- nothing to do with the C language. Sounds like an OS or network
- error.
- >
- >Is there any good reason why a C compiled program will always run
- >on its host machine but cause a problem on a non host, if so how
- >does one locate and correct such an error? Apart from compile it
- >on the non host machine!
- >
- If some TSR's (assuming DOS) is resident on one machine but
- not on the other, that could cause it. Your first step is to find
- out what the error message means and who is sending it -- it's
- not coming from DOS.
- --
-
- Pete
-
-
-
-
-
-